Updated commit message to add "Fixes #3250.".

Also, I have now verified that the regex still works for the 32-bit exe filename "ZusiSim.exe" after updating 32 bit dxvk dlls in the compatdata wine prefix (launching it from the command line using Proton's wine executable and the compatdata wine prefix simply works as expected, I thought there would be some DRM/Steam issues).

Thanks for the PR.
I see the game also have a bunch of editor exe's. Do you know if any of these need the same built in config to function properly?

That's a great question!

I've never used these editors and don't really know how to use them (they seem complicated), but giving them a very superficial test:

• ZusiFtdEditor.64.exe: This one appears broken with dxvk, with and without "noExplicitFrontBuffer". Instead of the cab view image, there is just a gray area with the cab view flickering for ~1 frame when clicking the gray area. This is not an issue when using wine d3d9 apparently.
• Zusi3DEditor.64.exe: I haven't noticed any obvious issues when not using the config.
• ZusiFzgEditor.64.exe, ZusiDateiverwaltung.exe: It seems like these don't use D3D
• ZusiGleisplanEditor.exe: Not sure how to launch this one (it attempts to launch using my wine-mono installation, even though it should probably use MS dotnet from the game's Proton wineprefix instead)

Thanks for the extra testing. I have asked besentv if he has any input on the last exe.

Edit: Would you be able to make a issue for the ZusiFtdEditor.64.exe problem?

Edit: Would you be able to make a issue for the ZusiFtdEditor.64.exe problem?

Sure, I'll try to find out what is going on, and then open an issue (if I can't find an existing issue for this problem).

Thanks for the review :-)

Not sure where to put this, about the ZusiFtdEditor.64.exe issue: I suspect it may not be a dxvk bug after all. There are two layers in that editor preview feature: The rendered cab view image itself (D3D9) as it would appear in the game, and an additional layer on top of it that draws rectangles around selected elements in the cab view. When using dxvk, only the "rectangle layer" is visible with gray areas inside and inbetween rectangles, instead of the cab view image. When not using dxvk, only the cab view layer is visible and rectangles are missing. So maybe dxvk is actually less buggy here, and wine just needs to learn to make those pixels in the "rectangle layer" that are not actually part of a rectangles transparent instead of opaque gray – or something along those lines. So I'd consider it "not a dxvk bug" for now.